Reassessing Brooks' Law for the Free Software Community
نویسندگان
چکیده
Proponents of Free Software have argued that some of the most established software engineering principles do not fully apply when considered in an open, distributed approach. Among these principles, “Brooks’ Law” has been questioned in the Free Software context: large teams of developers, contrary to the law, will not need an increasingly growing number of communication channels. As advocates claim, this is due to the internal characteristics of the Free Software process: the high modularity of the code helps developers to work on comparted sections, without the need to coordinate with all other contriutors. This paper examines Brooks’ Law in a Free Software context, and it studies the interaction of contributors to a large Free Software project, KDE. The network of interactions is analyzed and a summary term, the “compaction”, is dynamically evaluated to test how the coordination mechanism evolves over time in the project. This paper argues that the claim of advocates holds true, but with limitations: in the KDE project, the few initial developers needed a significant amount of communication. The growth of KDE brought the need to break the number of overall communication channels to a significant extent. Finally, an established amount of 300 developers currently needs the same amount of communication as when the developers were only 10. We interpret this result by arguing that Brooks’ Law holds true among the core developers of any large Free Software project.
منابع مشابه
Knowledge and Attitude toward Smoke-Free Legislation and Second-Hand Smoking Exposure among Workers in Indoor Bars, Beer Parlors and Discotheques in Osun State of Nigeria
Background One of the requirements of the Osun State smoke-free legislation is to ensure smoke-free enclosed and partially enclosed workplaces. This survey was conducted to assess the knowledge and attitude of workers in indoor bars, beer parlors and discotheques to smoke-free legislation in general and the Osun State smoke-free law in particular. Methods A convenience sampling of 36 hospital...
متن کاملBrooks' Law Revisited: A System Dynamics Approach
The Brooks’ Law says that adding manpower to a late software project makes it later. Brooks developed the law through observation of many projects and derived the generalization. His explanation was quite reasonable and convincing. However, it becomes a debilitating statement to any software project manager who is faced with a late project. This paper presents an in-depth study of Brooks’ Law u...
متن کاملTaxing the development structure of open source communities: An information processing view
a r t i c l e i n f o Committers in Free/Libre and Open Source Software (FLOSS) projects shoulder responsibility for evaluating contributions and coordinating the broader community development effort. Given committers' central role in development processes, we examine whether how they are organized influences FLOSS community performance. Specifically, drawing on the lens of Organizational Infor...
متن کاملBrooks' versus Linus' law: an empirical test of open source projects
findings, recommendations, and opinions expressed are those of the authors and do not reflect the views of the funding agency. Thanks go to Megan Conklin, Kevin Crowston and the FLOSSmole project team (http://ossmole .sourceforge.net/) for making their Sourceforge data available, and for their assistance. We are also grateful to Thomas Folz-Donahue for programming work building our FLOSS projec...
متن کاملCover Fe Ature
Twenty-five years ago, IBM software engineer Fred Brooks famously contended that " there is no single development , in either technology or management technique, which by itself promises even one order of magnitude improvement within a decade in productivity, in reliability, in simplicity. " 1 However, many claim that OSS is indeed such a silver bullet. Defenders argue that OSS, beyond its obvi...
متن کامل